Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cde87b331f3e709811617b60f27bdd2ca90e36271f1371b57ac830b59613120c

Tx prefix hash: f777db2297fbefbbc6edc7d5371465c9f65d42e8dc6bdf664c24221f60d5a41a
Tx public key: 5de5660839892fa5013b32896383bb87026e73b95b0c0d096791aa6f48f89462
Timestamp: 1733584003 Timestamp [UCT]: 2024-12-07 15:06:43 Age [y:d:h:m:s]: 00:156:15:54:02
Block: 1170073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111781 RingCT/type: yes/0
Extra: 015de5660839892fa5013b32896383bb87026e73b95b0c0d096791aa6f48f8946202110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4a611b447b6d6910d2b7920dbee86d5ea398efc7d820fd0c001dbf85105cce9 0.600000000000 1655802 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": 1170083, "vin": [ { "gen": { "height": 1170073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4a611b447b6d6910d2b7920dbee86d5ea398efc7d820fd0c001dbf85105cce9" } } ], "extra": [ 1, 93, 229, 102, 8, 57, 137, 47, 165, 1, 59, 50, 137, 99, 131, 187, 135, 2, 110, 115, 185, 91, 12, 13, 9, 103, 145, 170, 111, 72, 248, 148, 98, 2, 17, 0, 0, 0, 12, 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