Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e9a0f7301b2a43cab2fb3c77e826fa89884582ce05e75412b9426f23ce64a7f

Tx prefix hash: 6f9a7c4a8eb4be9ae9e22240c30b760389bc40a703b47526589f5202dc4d69c4
Tx public key: 17dd98cfc0181a073f425c1e26784bb035bf1582cd8bc9048401d3ad314ff8db
Timestamp: 1712753303 Timestamp [UCT]: 2024-04-10 12:48:23 Age [y:d:h:m:s]: 00:349:05:36:02
Block: 997451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249696 RingCT/type: yes/0
Extra: 0117dd98cfc0181a073f425c1e26784bb035bf1582cd8bc9048401d3ad314ff8db0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d00b8743758c531692e568b8b973e3c48af21a6dd5b25378b70c49e5eb82086 0.600000000000 1457883 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": 997461, "vin": [ { "gen": { "height": 997451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d00b8743758c531692e568b8b973e3c48af21a6dd5b25378b70c49e5eb82086" } } ], "extra": [ 1, 23, 221, 152, 207, 192, 24, 26, 7, 63, 66, 92, 30, 38, 120, 75, 176, 53, 191, 21, 130, 205, 139, 201, 4, 132, 1, 211, 173, 49, 79, 248, 219, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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