Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72567140c121c6dce8e5fe9978b1c3023e587efea5df85bb47ea3fde7d4afb4

Tx prefix hash: 8bada65c1767e767ce4b51430a4bb9cfaaaae74d342c6f951865d5f8c95f1c29
Tx public key: 4454e5ee5d25eb2736ea730201556ce20a4ca5edc5a2c0de417904716c95e185
Timestamp: 1726533656 Timestamp [UCT]: 2024-09-17 00:40:56 Age [y:d:h:m:s]: 00:201:03:52:27
Block: 1111718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143606 RingCT/type: yes/0
Extra: 014454e5ee5d25eb2736ea730201556ce20a4ca5edc5a2c0de417904716c95e18502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb1e65f84d24fa4e77df7a69aa9b10a295c4cf8bf36184b18ea6c57cd78679ba 0.600000000000 1590779 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": 1111728, "vin": [ { "gen": { "height": 1111718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb1e65f84d24fa4e77df7a69aa9b10a295c4cf8bf36184b18ea6c57cd78679ba" } } ], "extra": [ 1, 68, 84, 229, 238, 93, 37, 235, 39, 54, 234, 115, 2, 1, 85, 108, 226, 10, 76, 165, 237, 197, 162, 192, 222, 65, 121, 4, 113, 108, 149, 225, 133, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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