Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eac99e507b1464200e6a0e4182884fc1db0506f872dcef33463d370be2478bd

Tx prefix hash: a4880bc6592c801e8541ad5ea14de44098865c6f21427bbc8e8ed8a082c30b20
Tx public key: 4a69fc22a1472f78d76c4ae05e857b1483420f3ee529aa6fbaecee7d6029a303
Timestamp: 1721419224 Timestamp [UCT]: 2024-07-19 20:00:24 Age [y:d:h:m:s]: 00:264:02:36:20
Block: 1069353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188645 RingCT/type: yes/0
Extra: 014a69fc22a1472f78d76c4ae05e857b1483420f3ee529aa6fbaecee7d6029a303021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21916f0044e5231df7937f0ee877c7ac596a06482a11367c3e9f7f60d41e1584 0.600000000000 1540738 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": 1069363, "vin": [ { "gen": { "height": 1069353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21916f0044e5231df7937f0ee877c7ac596a06482a11367c3e9f7f60d41e1584" } } ], "extra": [ 1, 74, 105, 252, 34, 161, 71, 47, 120, 215, 108, 74, 224, 94, 133, 123, 20, 131, 66, 15, 62, 229, 41, 170, 111, 186, 236, 238, 125, 96, 41, 163, 3, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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