Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30570f13beeadb12167690ef3f2827d006376b6453c3f9fe078a22474b027fab

Tx prefix hash: 7b586cc1d5c381b5bc8e5a3c133c7880cac55b57ec1e75174dec9bc0a5c47a5e
Tx public key: df263d61c3d45c57ece912e8dbbd19edc2c162250eb926f40e618321e500f33c
Timestamp: 1718532635 Timestamp [UCT]: 2024-06-16 10:10:35 Age [y:d:h:m:s]: 00:220:02:45:57
Block: 1045412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157458 RingCT/type: yes/0
Extra: 01df263d61c3d45c57ece912e8dbbd19edc2c162250eb926f40e618321e500f33c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96197b61af212c4e160ae2833fb0281f4b93d754033f6a28e41c6124ce081c08 0.600000000000 1514975 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": 1045422, "vin": [ { "gen": { "height": 1045412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96197b61af212c4e160ae2833fb0281f4b93d754033f6a28e41c6124ce081c08" } } ], "extra": [ 1, 223, 38, 61, 97, 195, 212, 92, 87, 236, 233, 18, 232, 219, 189, 25, 237, 194, 193, 98, 37, 14, 185, 38, 244, 14, 97, 131, 33, 229, 0, 243, 60, 2, 17, 0, 0, 0, 3, 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