Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26971488200bcadae2d9f0181edf58e2a9e36c78425b20d6030c96ecccbe947f

Tx prefix hash: b49f0601206c6d1990e4c1bc4f9da74af5e7c11b5a9698506d7e787c41145404
Tx public key: 2ab32c7f9570b4fa9247e3478d79ae110a9a8257249947e3f70fcb0e3c5e549d
Timestamp: 1746692048 Timestamp [UCT]: 2025-05-08 08:14:08 Age [y:d:h:m:s]: 00:267:20:02:56
Block: 1278320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189048 RingCT/type: yes/0
Extra: 012ab32c7f9570b4fa9247e3478d79ae110a9a8257249947e3f70fcb0e3c5e549d0211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67f337f5de49d2a41e2a9624d17749f026617c38771f83cded03cba920bcb904 0.600000000000 1765685 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": 1278330, "vin": [ { "gen": { "height": 1278320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67f337f5de49d2a41e2a9624d17749f026617c38771f83cded03cba920bcb904" } } ], "extra": [ 1, 42, 179, 44, 127, 149, 112, 180, 250, 146, 71, 227, 71, 141, 121, 174, 17, 10, 154, 130, 87, 36, 153, 71, 227, 247, 15, 203, 14, 60, 94, 84, 157, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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