Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10a87c0d2edca6b3451906069677625b311cea6a94dfade8cb075f0856a89d2a

Tx prefix hash: 6348748677ddf71b018948e0fd5544fb29461fcb2f509e1de5223843dea01c20
Tx public key: bdc5cf6447e1b58fb2c99741f20397ccf63ceeda6b0fd5cf41de9c8db608cafd
Timestamp: 1705923465 Timestamp [UCT]: 2024-01-22 11:37:45 Age [y:d:h:m:s]: 01:084:18:49:49
Block: 940819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321709 RingCT/type: yes/0
Extra: 01bdc5cf6447e1b58fb2c99741f20397ccf63ceeda6b0fd5cf41de9c8db608cafd02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f33ae6beab344a1e9f404dc30c9a8ee26412c750e7fb13e70ba172d497d5cc8b 0.600000000000 1398959 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": 940829, "vin": [ { "gen": { "height": 940819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f33ae6beab344a1e9f404dc30c9a8ee26412c750e7fb13e70ba172d497d5cc8b" } } ], "extra": [ 1, 189, 197, 207, 100, 71, 225, 181, 143, 178, 201, 151, 65, 242, 3, 151, 204, 246, 60, 238, 218, 107, 15, 213, 207, 65, 222, 156, 141, 182, 8, 202, 253, 2, 17, 0, 0, 0, 9, 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