Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83bf38fe937653beace6627f4f5eefe41494a32749ec1e2ac3cd87e0009d77d4

Tx prefix hash: c36bceb17eedb7c95f36e9fa5bbc85dc59bddd78e4bb19ef034ddd54d8b8e5ec
Tx public key: 68f8506d126d94d78b9431b5a5fd537b157dc4f52154c5957b83f68bb0c5e5e0
Timestamp: 1737533166 Timestamp [UCT]: 2025-01-22 08:06:06 Age [y:d:h:m:s]: 00:328:12:21:28
Block: 1202721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232366 RingCT/type: yes/0
Extra: 0168f8506d126d94d78b9431b5a5fd537b157dc4f52154c5957b83f68bb0c5e5e0021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5225a3c8982b160d9bd68708b2f84bb55750fe14ca87a428a32af38c582c65b9 0.600000000000 1689386 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": 1202731, "vin": [ { "gen": { "height": 1202721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5225a3c8982b160d9bd68708b2f84bb55750fe14ca87a428a32af38c582c65b9" } } ], "extra": [ 1, 104, 248, 80, 109, 18, 109, 148, 215, 139, 148, 49, 181, 165, 253, 83, 123, 21, 125, 196, 245, 33, 84, 197, 149, 123, 131, 246, 139, 176, 197, 229, 224, 2, 17, 0, 0, 0, 1, 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