Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d9b03b804192dd587bf8d7a0fbdfb4b1e08dd2376150f836dda3730732b17b2

Tx prefix hash: 69406747b4ed2aa400d1b0cef3c344923d9a10acc5f3e043fad8f678a6332a51
Tx public key: e4e08d20d032e198f4208854e9eea261b12c87405d3d5b964897da93f21d14e6
Timestamp: 1732028072 Timestamp [UCT]: 2024-11-19 14:54:32 Age [y:d:h:m:s]: 00:204:23:05:28
Block: 1157178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146312 RingCT/type: yes/0
Extra: 01e4e08d20d032e198f4208854e9eea261b12c87405d3d5b964897da93f21d14e6021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44007c01586d5499c2fd70ab19fda7f686c63333ddb1d5fa78c3d7d13c8b4827 0.600000000000 1642801 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": 1157188, "vin": [ { "gen": { "height": 1157178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44007c01586d5499c2fd70ab19fda7f686c63333ddb1d5fa78c3d7d13c8b4827" } } ], "extra": [ 1, 228, 224, 141, 32, 208, 50, 225, 152, 244, 32, 136, 84, 233, 238, 162, 97, 177, 44, 135, 64, 93, 61, 91, 150, 72, 151, 218, 147, 242, 29, 20, 230, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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