Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36c7d6aa312c31b29b39578646f71cd7b7286ab2fac10e00b2c07fe50c466b7c

Tx prefix hash: a29a0dc48594eded1b341753d9d74d61ff325588185c5968bf3febca663b07d8
Tx public key: 30eedc3a7bdedf158f09921248bb818ba15a248acb8e5ddb01158e14f66fadb4
Timestamp: 1697005023 Timestamp [UCT]: 2023-10-11 06:17:03 Age [y:d:h:m:s]: 01:097:16:32:01
Block: 867120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331067 RingCT/type: yes/0
Extra: 0130eedc3a7bdedf158f09921248bb818ba15a248acb8e5ddb01158e14f66fadb4021100000002faf35c9c000000000000000000

1 output(s) for total of 0.821999423000 dcy

stealth address amount amount idx
00: 21ed73140df8f5a8230790164c2cfa5d8449d88b6cc94aa16d35fd7780d76b9a 0.821999423000 1321774 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": 867130, "vin": [ { "gen": { "height": 867120 } } ], "vout": [ { "amount": 821999423, "target": { "key": "21ed73140df8f5a8230790164c2cfa5d8449d88b6cc94aa16d35fd7780d76b9a" } } ], "extra": [ 1, 48, 238, 220, 58, 123, 222, 223, 21, 143, 9, 146, 18, 72, 187, 129, 139, 161, 90, 36, 138, 203, 142, 93, 219, 1, 21, 142, 20, 246, 111, 173, 180, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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