Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d03dbfe592d47601b4a55f7564d221c5c5e8b2cb89b3eda4e1eab6b2a2d51c7

Tx prefix hash: d5f871ad46a7e28624d413678822ca303cd0c6414fbc3b035ae0cf483752db3d
Tx public key: 646b194f6c4afbc24afe731b1479b03664240258e8b6544fc914de0b368ec383
Timestamp: 1705501770 Timestamp [UCT]: 2024-01-17 14:29:30 Age [y:d:h:m:s]: 01:082:21:47:50
Block: 937337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320361 RingCT/type: yes/0
Extra: 01646b194f6c4afbc24afe731b1479b03664240258e8b6544fc914de0b368ec38302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6421b900265e3dda4568c563c35c0c7535d2c5af3aa622c6aaa1dbdc3338107f 0.600000000000 1395387 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": 937347, "vin": [ { "gen": { "height": 937337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6421b900265e3dda4568c563c35c0c7535d2c5af3aa622c6aaa1dbdc3338107f" } } ], "extra": [ 1, 100, 107, 25, 79, 108, 74, 251, 194, 74, 254, 115, 27, 20, 121, 176, 54, 100, 36, 2, 88, 232, 182, 84, 79, 201, 20, 222, 11, 54, 142, 195, 131, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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