Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89ce1189e86169b9d1b0887e92e0d026f5c8dabd3676ed647156a03dfdb685db

Tx prefix hash: 934260ad03fb62b4edf94a4eba8d390cf05f925cf7c5b47409b124c5e4b5e476
Tx public key: d3fc41e68152c08beff24f557aef41d42ba78f932dec51cbb31c99ea10aa90e1
Timestamp: 1717109800 Timestamp [UCT]: 2024-05-30 22:56:40 Age [y:d:h:m:s]: 01:162:03:53:03
Block: 1033586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374484 RingCT/type: yes/0
Extra: 01d3fc41e68152c08beff24f557aef41d42ba78f932dec51cbb31c99ea10aa90e102110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdd55ae82578eff2006c8d4d5b9e457b94f75cc4b91219ae0e4f1a6ed581d03a 0.600000000000 1502057 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": 1033596, "vin": [ { "gen": { "height": 1033586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdd55ae82578eff2006c8d4d5b9e457b94f75cc4b91219ae0e4f1a6ed581d03a" } } ], "extra": [ 1, 211, 252, 65, 230, 129, 82, 192, 139, 239, 242, 79, 85, 122, 239, 65, 212, 43, 167, 143, 147, 45, 236, 81, 203, 179, 28, 153, 234, 16, 170, 144, 225, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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