Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f05e5ea503d1fd2625a4e0b8fcc7a2039d4d37186ff4a1c6730796cbc5f0afe1

Tx prefix hash: 707137a68cfd1d3e06cfd8f74c9f3521e492d4ef7bcb6c742f0038626367917d
Tx public key: 5364fb0acd42d8460dff9c7e4467c7f9d1a1a3cc986e89f9041d104a0654566f
Timestamp: 1734365599 Timestamp [UCT]: 2024-12-16 16:13:19 Age [y:d:h:m:s]: 00:092:18:31:08
Block: 1176556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66094 RingCT/type: yes/0
Extra: 015364fb0acd42d8460dff9c7e4467c7f9d1a1a3cc986e89f9041d104a0654566f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 317c06c0e03c668b0be491371f3d700b935f73754eb1292c8462d9cd1a6a86b9 0.600000000000 1662909 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": 1176566, "vin": [ { "gen": { "height": 1176556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "317c06c0e03c668b0be491371f3d700b935f73754eb1292c8462d9cd1a6a86b9" } } ], "extra": [ 1, 83, 100, 251, 10, 205, 66, 216, 70, 13, 255, 156, 126, 68, 103, 199, 249, 209, 161, 163, 204, 152, 110, 137, 249, 4, 29, 16, 74, 6, 84, 86, 111, 2, 17, 0, 0, 0, 3, 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