Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc850a050ac44c805ef6cdc537e15510f46fcf3160803f0ecdcd086f73ef9a18

Tx prefix hash: 09024c4ca767f85792531d1dab7582991eb668763ae64dfa3f0d124f15e7a6e8
Tx public key: 6d2b74eceff86fa4d6ff3b2f9bee5c1be6158bde605d8e9f161c6eb68a789814
Timestamp: 1715392658 Timestamp [UCT]: 2024-05-11 01:57:38 Age [y:d:h:m:s]: 00:259:02:09:22
Block: 1019375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185369 RingCT/type: yes/0
Extra: 016d2b74eceff86fa4d6ff3b2f9bee5c1be6158bde605d8e9f161c6eb68a78981402110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 451da7c5c5b46276d55fe6344d6403ff9e659fbaafb4d5aa24eb08e3d6949f0b 0.600000000000 1483328 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": 1019385, "vin": [ { "gen": { "height": 1019375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "451da7c5c5b46276d55fe6344d6403ff9e659fbaafb4d5aa24eb08e3d6949f0b" } } ], "extra": [ 1, 109, 43, 116, 236, 239, 248, 111, 164, 214, 255, 59, 47, 155, 238, 92, 27, 230, 21, 139, 222, 96, 93, 142, 159, 22, 28, 110, 182, 138, 120, 152, 20, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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