Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 073e9495647a4482e8a6052e0dee8da0e1a17279288f0a77de1b854afaae44e3

Tx prefix hash: 530e4115d183d68822bb1269b4a4e03f8948c8ff45d3f1efea2766d9a48249e2
Tx public key: 183acebb834982cd802e47d9b051cb99179072f9b0a9115f28461618ea9dd411
Timestamp: 1721640723 Timestamp [UCT]: 2024-07-22 09:32:03 Age [y:d:h:m:s]: 00:261:18:05:47
Block: 1071156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186998 RingCT/type: yes/0
Extra: 01183acebb834982cd802e47d9b051cb99179072f9b0a9115f28461618ea9dd411021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcfd953f10c2cbbf385a31e4061cd06528d6e90f1694236aad0fc790cb3cb54f 0.600000000000 1543273 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": 1071166, "vin": [ { "gen": { "height": 1071156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcfd953f10c2cbbf385a31e4061cd06528d6e90f1694236aad0fc790cb3cb54f" } } ], "extra": [ 1, 24, 58, 206, 187, 131, 73, 130, 205, 128, 46, 71, 217, 176, 81, 203, 153, 23, 144, 114, 249, 176, 169, 17, 95, 40, 70, 22, 24, 234, 157, 212, 17, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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