Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76f6841b99be93529f3918214caff5005e216bcc1e2c988a47763d62ee5336c2

Tx prefix hash: 46f70f7bc30e0dcd608bc4638d096bdaed7f8c8babffb87bcf8aabfc38e2d4be
Tx public key: 34049e29a10fd13a6abf0effebc15b667504487ddfc8557d78f68d6a5b2abd4d
Timestamp: 1734025892 Timestamp [UCT]: 2024-12-12 17:51:32 Age [y:d:h:m:s]: 00:096:16:47:01
Block: 1173748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68900 RingCT/type: yes/0
Extra: 0134049e29a10fd13a6abf0effebc15b667504487ddfc8557d78f68d6a5b2abd4d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc9e86e7b0e5a59faef8946767e7832eef1c922549e1f0963bce4da8b185b414 0.600000000000 1659803 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": 1173758, "vin": [ { "gen": { "height": 1173748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc9e86e7b0e5a59faef8946767e7832eef1c922549e1f0963bce4da8b185b414" } } ], "extra": [ 1, 52, 4, 158, 41, 161, 15, 209, 58, 106, 191, 14, 255, 235, 193, 91, 102, 117, 4, 72, 125, 223, 200, 85, 125, 120, 246, 141, 106, 91, 42, 189, 77, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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