Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dae0241c9eac191c4bdaf9a45bada8891e5aeb36a2b16b3588e3a709c80e3338

Tx prefix hash: 867f044e4205198a95a9a1ee1753bd4e1edd256d035a220e7ee3d4688220c536
Tx public key: 806dce95482bdb403253d6ba06607e9bffc9a205b5fef0c99b8d58cd2e97e48f
Timestamp: 1710119474 Timestamp [UCT]: 2024-03-11 01:11:14 Age [y:d:h:m:s]: 01:067:12:31:31
Block: 975651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309272 RingCT/type: yes/0
Extra: 01806dce95482bdb403253d6ba06607e9bffc9a205b5fef0c99b8d58cd2e97e48f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e88848da58ec2bdc38ae6bcefdccf388270f0a1d21e6bf14014993d85a142ddb 0.600000000000 1435624 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": 975661, "vin": [ { "gen": { "height": 975651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e88848da58ec2bdc38ae6bcefdccf388270f0a1d21e6bf14014993d85a142ddb" } } ], "extra": [ 1, 128, 109, 206, 149, 72, 43, 219, 64, 50, 83, 214, 186, 6, 96, 126, 155, 255, 201, 162, 5, 181, 254, 240, 201, 155, 141, 88, 205, 46, 151, 228, 143, 2, 17, 0, 0, 0, 1, 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