Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7ebcb227db87ccd03b7f639a6e88e0625db8e8bbc182e0419df92ececb97c53

Tx prefix hash: d1c5a8e802f5beb3986b0da722d3a03ce0d99c00abb7daf8e322c4fdff004a58
Tx public key: 310cb12b4f04d51114494dcfec2cbb76701975279914eb6da23b7df8ee18bd22
Timestamp: 1682602369 Timestamp [UCT]: 2023-04-27 13:32:49 Age [y:d:h:m:s]: 01:183:17:51:25
Block: 747762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392778 RingCT/type: yes/0
Extra: 01310cb12b4f04d51114494dcfec2cbb76701975279914eb6da23b7df8ee18bd22021100000003b3164c24000000000000000000

1 output(s) for total of 2.043404237000 dcy

stealth address amount amount idx
00: bc75c44b3474626cf8f7f7221ef4d5f21638f290447a7aedba80d9670e0b2844 2.043404237000 1195513 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": 747772, "vin": [ { "gen": { "height": 747762 } } ], "vout": [ { "amount": 2043404237, "target": { "key": "bc75c44b3474626cf8f7f7221ef4d5f21638f290447a7aedba80d9670e0b2844" } } ], "extra": [ 1, 49, 12, 177, 43, 79, 4, 213, 17, 20, 73, 77, 207, 236, 44, 187, 118, 112, 25, 117, 39, 153, 20, 235, 109, 162, 59, 125, 248, 238, 24, 189, 34, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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