Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f70c066504771f6a499589e36da8c2a0631cb09fdc3cd42908ed05fd06fe623

Tx prefix hash: 54729524f0b48b5e56ed5728fdf12620c82e8e4287a13337f31866102a7755b1
Tx public key: a4f9188f39b2f2621e4aee03df41587fcb56629b4ffd9f6787d67b10fe76f8b6
Timestamp: 1733764368 Timestamp [UCT]: 2024-12-09 17:12:48 Age [y:d:h:m:s]: 00:190:09:21:21
Block: 1171568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135788 RingCT/type: yes/0
Extra: 01a4f9188f39b2f2621e4aee03df41587fcb56629b4ffd9f6787d67b10fe76f8b6021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22f4016ce02fb8f724485f9c495ed853bbcaf2c403898bb99b592325d854c205 0.600000000000 1657343 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": 1171578, "vin": [ { "gen": { "height": 1171568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22f4016ce02fb8f724485f9c495ed853bbcaf2c403898bb99b592325d854c205" } } ], "extra": [ 1, 164, 249, 24, 143, 57, 178, 242, 98, 30, 74, 238, 3, 223, 65, 88, 127, 203, 86, 98, 155, 79, 253, 159, 103, 135, 214, 123, 16, 254, 118, 248, 182, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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