Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adab86313c92606df6a0c635ddbf6d50732d341334afa64944be1bb0b1cd004f

Tx prefix hash: 0c3d24fbc0526d46c06d0d4bdd34e4557af9b9b48f4135f0e9875615a7e73ba0
Tx public key: ec7fcec5ae39b391583eea8b4b6b48239b6b29224c40358b46fb1e88eeaea446
Timestamp: 1574469698 Timestamp [UCT]: 2019-11-23 00:41:38 Age [y:d:h:m:s]: 05:008:02:39:52
Block: 14884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1149108 RingCT/type: yes/0
Extra: 01ec7fcec5ae39b391583eea8b4b6b48239b6b29224c40358b46fb1e88eeaea446021100000005b63f0b49000000000000000000

1 output(s) for total of 547.878191704000 dcy

stealth address amount amount idx
00: bcca5479fd9e85d37fd246bb0b00ab3c6d6dbb44e7180335aaf8ba4a51f94a6a 547.878191704000 19396 of 0

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": 14894, "vin": [ { "gen": { "height": 14884 } } ], "vout": [ { "amount": 547878191704, "target": { "key": "bcca5479fd9e85d37fd246bb0b00ab3c6d6dbb44e7180335aaf8ba4a51f94a6a" } } ], "extra": [ 1, 236, 127, 206, 197, 174, 57, 179, 145, 88, 62, 234, 139, 75, 107, 72, 35, 155, 107, 41, 34, 76, 64, 53, 139, 70, 251, 30, 136, 238, 174, 164, 70, 2, 17, 0, 0, 0, 5, 182, 63, 11, 73, 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