Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc61feb5de75e40d888a26f8b72bd21cd26bac38b1878321a9ccf181d96bf3e8

Tx prefix hash: bd760a1330a9e5ed21d024c21910bb87eec91899244fbfc8f3c51ddffa86fb75
Tx public key: 6e20dddde573ac2b1f96f73bbfd2ae52cf7266c270e6510e9e1b261c17c66fe3
Timestamp: 1744800936 Timestamp [UCT]: 2025-04-16 10:55:36 Age [y:d:h:m:s]: 00:038:03:35:57
Block: 1262664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27295 RingCT/type: yes/0
Extra: 016e20dddde573ac2b1f96f73bbfd2ae52cf7266c270e6510e9e1b261c17c66fe3021100000006dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b5db90cc2a956b9ab2a21130d587ef068831ff94e6d678f51a90909434127a4 0.600000000000 1749847 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": 1262674, "vin": [ { "gen": { "height": 1262664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b5db90cc2a956b9ab2a21130d587ef068831ff94e6d678f51a90909434127a4" } } ], "extra": [ 1, 110, 32, 221, 221, 229, 115, 172, 43, 31, 150, 247, 59, 191, 210, 174, 82, 207, 114, 102, 194, 112, 230, 81, 14, 158, 27, 38, 28, 23, 198, 111, 227, 2, 17, 0, 0, 0, 6, 219, 181, 113, 193, 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