Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55d6a60e930b6ecfe97664aa983a53272d8eceee1764406ca0cc925df8847bb9

Tx prefix hash: 6bf9d2c6e07dfcac23c82b651a80ca2369707e39f5a9ddac08da48dff6c50001
Tx public key: f9b7f848e593aea813cf9f6e232f32345de3649e5113b7eb402ba2215c615d8d
Timestamp: 1727445812 Timestamp [UCT]: 2024-09-27 14:03:32 Age [y:d:h:m:s]: 00:117:05:13:50
Block: 1119285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83765 RingCT/type: yes/0
Extra: 01f9b7f848e593aea813cf9f6e232f32345de3649e5113b7eb402ba2215c615d8d02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ee0270d1eaf1739275e7a07a221ecbf5e18de8180ef1e7cf8bc43fbb14bc2ce 0.600000000000 1600786 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": 1119295, "vin": [ { "gen": { "height": 1119285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ee0270d1eaf1739275e7a07a221ecbf5e18de8180ef1e7cf8bc43fbb14bc2ce" } } ], "extra": [ 1, 249, 183, 248, 72, 229, 147, 174, 168, 19, 207, 159, 110, 35, 47, 50, 52, 93, 227, 100, 158, 81, 19, 183, 235, 64, 43, 162, 33, 92, 97, 93, 141, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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