Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 972c786f047986a0a452097ba65f9b57c34e8fd2c756ea177a31a3b51b0b4f83

Tx prefix hash: 2929b0416d3172220b36790a4f466613d7b30b479b1fe84d5aaacabcb160206d
Tx public key: 5ba8278a6babc9137bc5220d13921caa5e824b47f8e078412ddd48ce0efe879e
Timestamp: 1751300243 Timestamp [UCT]: 2025-06-30 16:17:23 Age [y:d:h:m:s]: 00:192:03:33:46
Block: 1315953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135602 RingCT/type: yes/0
Extra: 015ba8278a6babc9137bc5220d13921caa5e824b47f8e078412ddd48ce0efe879e02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efba0386c1a286a07a0ecb1d3f3c1033321b8c3a8365d2b0278472d0fc218b96 0.600000000000 1803610 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": 1315963, "vin": [ { "gen": { "height": 1315953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efba0386c1a286a07a0ecb1d3f3c1033321b8c3a8365d2b0278472d0fc218b96" } } ], "extra": [ 1, 91, 168, 39, 138, 107, 171, 201, 19, 123, 197, 34, 13, 19, 146, 28, 170, 94, 130, 75, 71, 248, 224, 120, 65, 45, 221, 72, 206, 14, 254, 135, 158, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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