Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6c464b9e0f5f47fc55dc9d7f70f1af00b965a12af5083ed579aa8c02fd70ef4b

Tx prefix hash: 310ce4349af24687a3a7bce64842454887f10416738132916c5e71db383651e2
Tx public key: bb824cc73df977e4b483995212a0cfe2d53931b20259fad74d9a7f2d4c1df1d1
Timestamp: 1759885589 Timestamp [UCT]: 2025-10-08 01:06:29 Age [y:d:h:m:s]: 00:033:06:31:10
Block: 1385102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23835 RingCT/type: yes/0
Extra: 01bb824cc73df977e4b483995212a0cfe2d53931b20259fad74d9a7f2d4c1df1d1021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2857131cd06e88028dcb25ac33bdf1b21a65bcaf2b7553377015a7e09d55ee4f 0.600000000000 1873259 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1385112, "vin": [ { "gen": { "height": 1385102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2857131cd06e88028dcb25ac33bdf1b21a65bcaf2b7553377015a7e09d55ee4f" } } ], "extra": [ 1, 187, 130, 76, 199, 61, 249, 119, 228, 180, 131, 153, 82, 18, 160, 207, 226, 213, 57, 49, 178, 2, 89, 250, 215, 77, 154, 127, 45, 76, 29, 241, 209, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8