Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87a099dce1c78f5a39f2a96a07ebc74b652bc6be5ad479ebac55fd6c563ada1a

Tx prefix hash: f2fc57513916453ce04b5d3cddb0e3ebea04a690a314c22d949829c4ee576474
Tx public key: 56ecfa3e0c480adbab11a64323841a2423e059e992f01c542e2762a132f335a1
Timestamp: 1733345401 Timestamp [UCT]: 2024-12-04 20:50:01 Age [y:d:h:m:s]: 00:122:08:56:57
Block: 1168100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87255 RingCT/type: yes/0
Extra: 0156ecfa3e0c480adbab11a64323841a2423e059e992f01c542e2762a132f335a1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c1cf9d52577bc6c121818c30ab87ea97edc2c9a4d13a26792f912840c3b6e0d 0.600000000000 1653807 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": 1168110, "vin": [ { "gen": { "height": 1168100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c1cf9d52577bc6c121818c30ab87ea97edc2c9a4d13a26792f912840c3b6e0d" } } ], "extra": [ 1, 86, 236, 250, 62, 12, 72, 10, 219, 171, 17, 166, 67, 35, 132, 26, 36, 35, 224, 89, 233, 146, 240, 28, 84, 46, 39, 98, 161, 50, 243, 53, 161, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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