Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 441392208a91c70fb8685c97f56a9d5c03dd2fb4b75e9e43f7a06da5996671d1

Tx prefix hash: b7a35917b9f8f054b9094d63eeddcbb4daad4ffb4e0eab44b17b5d1bfe43043d
Tx public key: 949e3b981a7363467603b1e79d9772dba96917dea6509d171155e641446e64f2
Timestamp: 1729760716 Timestamp [UCT]: 2024-10-24 09:05:16 Age [y:d:h:m:s]: 00:237:19:58:23
Block: 1138441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169686 RingCT/type: yes/0
Extra: 01949e3b981a7363467603b1e79d9772dba96917dea6509d171155e641446e64f2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7b5f7aa8d17593129bdd6c581ec371fd6a7201ebc4b37119b0b98dc26a3c0fb 0.600000000000 1622114 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": 1138451, "vin": [ { "gen": { "height": 1138441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7b5f7aa8d17593129bdd6c581ec371fd6a7201ebc4b37119b0b98dc26a3c0fb" } } ], "extra": [ 1, 148, 158, 59, 152, 26, 115, 99, 70, 118, 3, 177, 231, 157, 151, 114, 219, 169, 105, 23, 222, 166, 80, 157, 23, 17, 85, 230, 65, 68, 110, 100, 242, 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