Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e04e604108b9baa9c9aaf493b189d1e90459d3bcba02c1e31ce693f6ab06d2c4

Tx prefix hash: 8d822cd3abac6be78ca0abc92d29825fdb8e35e15909d7fb1be16f7ecff5eeb9
Tx public key: f52896d5099dd688efe5d7902932288f03d7f0fb77d2f110cdb3820900005732
Timestamp: 1705424185 Timestamp [UCT]: 2024-01-16 16:56:25 Age [y:d:h:m:s]: 01:079:19:19:50
Block: 936696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318145 RingCT/type: yes/0
Extra: 01f52896d5099dd688efe5d7902932288f03d7f0fb77d2f110cdb382090000573202110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a6d2f0afe4b5983e2ea1046a0e7424fd88813b2c25dd1660661ada9e2022a0e 0.600000000000 1394734 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": 936706, "vin": [ { "gen": { "height": 936696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a6d2f0afe4b5983e2ea1046a0e7424fd88813b2c25dd1660661ada9e2022a0e" } } ], "extra": [ 1, 245, 40, 150, 213, 9, 157, 214, 136, 239, 229, 215, 144, 41, 50, 40, 143, 3, 215, 240, 251, 119, 210, 241, 16, 205, 179, 130, 9, 0, 0, 87, 50, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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