Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5130d9e6df90c6e7b7d572b434dacc5bd5bf4cdd218249eff0144a03cd48f85

Tx prefix hash: 32621c87354cbaa817d035cb93a4175cb45ccd2488458a7896edd82674214482
Tx public key: 1014ec58eae946b6a1500df70dc2b580772fa96d04c7edf82809486678d4c7f3
Timestamp: 1722731725 Timestamp [UCT]: 2024-08-04 00:35:25 Age [y:d:h:m:s]: 00:300:11:51:49
Block: 1080205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214712 RingCT/type: yes/0
Extra: 011014ec58eae946b6a1500df70dc2b580772fa96d04c7edf82809486678d4c7f302110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b8df4b95c1d3c61be318b02b96aa92a4519abf639893b5563b96bea82f77bd5 0.600000000000 1553478 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": 1080215, "vin": [ { "gen": { "height": 1080205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b8df4b95c1d3c61be318b02b96aa92a4519abf639893b5563b96bea82f77bd5" } } ], "extra": [ 1, 16, 20, 236, 88, 234, 233, 70, 182, 161, 80, 13, 247, 13, 194, 181, 128, 119, 47, 169, 109, 4, 199, 237, 248, 40, 9, 72, 102, 120, 212, 199, 243, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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