Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11190d355531f155511d3b2803d5bd491c6c49b489fea5afd317d6e90622af0f

Tx prefix hash: 965cbc9711116bf5afa27c1336d77f7dd28ef62f447a95782ccfeb117bdc93e7
Tx public key: edf26ed489714274ef67eb9fbfa149ae021683b4d2d183fc337ed618f6a46df5
Timestamp: 1732426899 Timestamp [UCT]: 2024-11-24 05:41:39 Age [y:d:h:m:s]: 00:133:09:53:19
Block: 1160482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95154 RingCT/type: yes/0
Extra: 01edf26ed489714274ef67eb9fbfa149ae021683b4d2d183fc337ed618f6a46df50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a25d26e7fea3c8218daa77d430d4ac5344a4db915dcb1fc5f3f6b62bc9bf276 0.600000000000 1646129 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": 1160492, "vin": [ { "gen": { "height": 1160482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a25d26e7fea3c8218daa77d430d4ac5344a4db915dcb1fc5f3f6b62bc9bf276" } } ], "extra": [ 1, 237, 242, 110, 212, 137, 113, 66, 116, 239, 103, 235, 159, 191, 161, 73, 174, 2, 22, 131, 180, 210, 209, 131, 252, 51, 126, 214, 24, 246, 164, 109, 245, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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