Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cec2eb3b9b79683efd4471e51d8cd6a41da05fca09683212f1ab92d5d2e85a0

Tx prefix hash: f52d764f1dfb8e31897192dbf2b0796a3c9450fcdaa9739cc63b11f4e81efcaa
Tx public key: b1fe8a6b1a2292a18c605e409a5f4045b00ae2068f437423cd461343cd398195
Timestamp: 1737312620 Timestamp [UCT]: 2025-01-19 18:50:20 Age [y:d:h:m:s]: 00:150:18:16:16
Block: 1200918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107460 RingCT/type: yes/0
Extra: 01b1fe8a6b1a2292a18c605e409a5f4045b00ae2068f437423cd461343cd39819502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9920a08e0df43b69126c66129c3d54be2d49ec7cd78e57e0c55d428cefddfe3 0.600000000000 1687565 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": 1200928, "vin": [ { "gen": { "height": 1200918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9920a08e0df43b69126c66129c3d54be2d49ec7cd78e57e0c55d428cefddfe3" } } ], "extra": [ 1, 177, 254, 138, 107, 26, 34, 146, 161, 140, 96, 94, 64, 154, 95, 64, 69, 176, 10, 226, 6, 143, 67, 116, 35, 205, 70, 19, 67, 205, 57, 129, 149, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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