Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb90284aefd7c7c75194c6740c4ec68c5a0ed2f93e62ebd5c1749d868e7eccd1

Tx prefix hash: a84481c04af8488339bf4996686f13c85c490511c37e6dfafc2f116a09a4fb6e
Tx public key: 038640fa2524adaa6e4a3245195fcdbe58c9d828a7af20a21b62faa5f78bfe20
Timestamp: 1749706638 Timestamp [UCT]: 2025-06-12 05:37:18 Age [y:d:h:m:s]: 00:162:19:21:18
Block: 1303247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114072 RingCT/type: yes/0
Extra: 01038640fa2524adaa6e4a3245195fcdbe58c9d828a7af20a21b62faa5f78bfe2002110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19e3c8f866b8df3b8d36e67f6c6359ea97b9e5e8e043dcf030cc39d9361ce03d 0.600000000000 1790824 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": 1303257, "vin": [ { "gen": { "height": 1303247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19e3c8f866b8df3b8d36e67f6c6359ea97b9e5e8e043dcf030cc39d9361ce03d" } } ], "extra": [ 1, 3, 134, 64, 250, 37, 36, 173, 170, 110, 74, 50, 69, 25, 95, 205, 190, 88, 201, 216, 40, 167, 175, 32, 162, 27, 98, 250, 165, 247, 139, 254, 32, 2, 17, 0, 0, 0, 2, 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