Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0e466374b63125a25fd454b4e5cf97dc2fca084f350658b6a6d5504ac431057

Tx prefix hash: 91a0d38cb217b999db7df39336a6e8415feb9b4ea868f224b731061348bcd8c5
Tx public key: d5f462ebc76435e926763d31b49dc3612037e64d10e140a8cc3e3fb5bb1cfc45
Timestamp: 1714378213 Timestamp [UCT]: 2024-04-29 08:10:13 Age [y:d:h:m:s]: 00:256:05:18:07
Block: 1010951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183387 RingCT/type: yes/0
Extra: 01d5f462ebc76435e926763d31b49dc3612037e64d10e140a8cc3e3fb5bb1cfc450211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c9192edc7bf350ca87d46cc68d25dc37f601f906c21bb048d9d05105f996860 0.600000000000 1473041 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": 1010961, "vin": [ { "gen": { "height": 1010951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c9192edc7bf350ca87d46cc68d25dc37f601f906c21bb048d9d05105f996860" } } ], "extra": [ 1, 213, 244, 98, 235, 199, 100, 53, 233, 38, 118, 61, 49, 180, 157, 195, 97, 32, 55, 230, 77, 16, 225, 64, 168, 204, 62, 63, 181, 187, 28, 252, 69, 2, 17, 0, 0, 0, 16, 122, 156, 244, 199, 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