Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 332866f68fb4c198abce933413c100f9e614fcc4f6a7cc0d4d1b85086f463df4

Tx prefix hash: 8d83b31756d086842901c36997d96cd8a013cfabae9dd8801015bf81403ce356
Tx public key: 0e50b43577125789ab9e73b2a3742ad79f87ae2143ad242a7664a2f76ec1f6c0
Timestamp: 1717572279 Timestamp [UCT]: 2024-06-05 07:24:39 Age [y:d:h:m:s]: 00:296:16:41:52
Block: 1037439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212029 RingCT/type: yes/0
Extra: 010e50b43577125789ab9e73b2a3742ad79f87ae2143ad242a7664a2f76ec1f6c002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e5e4630c9a97a327fa2f22853ac00565b9b583c2afb7c8b6dcd91c52ed8287e 0.600000000000 1505970 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": 1037449, "vin": [ { "gen": { "height": 1037439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e5e4630c9a97a327fa2f22853ac00565b9b583c2afb7c8b6dcd91c52ed8287e" } } ], "extra": [ 1, 14, 80, 180, 53, 119, 18, 87, 137, 171, 158, 115, 178, 163, 116, 42, 215, 159, 135, 174, 33, 67, 173, 36, 42, 118, 100, 162, 247, 110, 193, 246, 192, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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