Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e4c9f5a76056763d72cfd8eee679d34da3df9b7329061ca54ef6b46d47eb1ee

Tx prefix hash: 0d02a75b198b0279303a270d80475cb45d37871fff24ce1a73cfe8721f2c1b5f
Tx public key: fd5097836f6c952df36d61b97202d85300082d64b98db71fc094cdba4d3a254f
Timestamp: 1728929671 Timestamp [UCT]: 2024-10-14 18:14:31 Age [y:d:h:m:s]: 01:020:14:45:20
Block: 1131586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273098 RingCT/type: yes/0
Extra: 01fd5097836f6c952df36d61b97202d85300082d64b98db71fc094cdba4d3a254f02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0870a93dc4ad4a91a104409ad177d15b7dbd4366e8d882017eaf47b2ee1ef7bd 0.600000000000 1614489 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": 1131596, "vin": [ { "gen": { "height": 1131586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0870a93dc4ad4a91a104409ad177d15b7dbd4366e8d882017eaf47b2ee1ef7bd" } } ], "extra": [ 1, 253, 80, 151, 131, 111, 108, 149, 45, 243, 109, 97, 185, 114, 2, 216, 83, 0, 8, 45, 100, 185, 141, 183, 31, 192, 148, 205, 186, 77, 58, 37, 79, 2, 17, 0, 0, 0, 1, 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