Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf72723c195e7dab4e85bb632153b955aff95e5e8f885175f4434054cf70b02

Tx prefix hash: 7d6f80a2bdbfa8fd185808339f514b163b9ca0b183dfdf0a6c105bf6c9c36911
Tx public key: e7432384dfce481bab4d9911d231fcd5365a70e911f9e893e9e38e5238c8a502
Timestamp: 1684451856 Timestamp [UCT]: 2023-05-18 23:17:36 Age [y:d:h:m:s]: 02:170:05:20:07
Block: 763096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 641457 RingCT/type: yes/0
Extra: 01e7432384dfce481bab4d9911d231fcd5365a70e911f9e893e9e38e5238c8a50202110000000475e3f0e9000000000000000000

1 output(s) for total of 1.817801091000 dcy

stealth address amount amount idx
00: 019719f4ec9a558be52e67a51dfb97ce58392417e69e96887ff86356f19281d2 1.817801091000 1211893 of 0

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": 763106, "vin": [ { "gen": { "height": 763096 } } ], "vout": [ { "amount": 1817801091, "target": { "key": "019719f4ec9a558be52e67a51dfb97ce58392417e69e96887ff86356f19281d2" } } ], "extra": [ 1, 231, 67, 35, 132, 223, 206, 72, 27, 171, 77, 153, 17, 210, 49, 252, 213, 54, 90, 112, 233, 17, 249, 232, 147, 233, 227, 142, 82, 56, 200, 165, 2, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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