Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b840049bb9ea76d3a3e2475917e501fcadab952465456eb9183195fb6ee135

Tx prefix hash: c01583341d729a40410119cb902f4622eed7331923d2b516c07710bf4fcf6b3a
Tx public key: e503e74affc7c10a42336af095490f2d4c6c15c8be3ff807bf8682a33a7270c0
Timestamp: 1737008289 Timestamp [UCT]: 2025-01-16 06:18:09 Age [y:d:h:m:s]: 00:060:04:58:50
Block: 1198408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42830 RingCT/type: yes/0
Extra: 01e503e74affc7c10a42336af095490f2d4c6c15c8be3ff807bf8682a33a7270c00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bbd59134c160fbfe1cdf733457120e5e86edec92f0fa23ba277a57da500f9c4 0.600000000000 1685033 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": 1198418, "vin": [ { "gen": { "height": 1198408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bbd59134c160fbfe1cdf733457120e5e86edec92f0fa23ba277a57da500f9c4" } } ], "extra": [ 1, 229, 3, 231, 74, 255, 199, 193, 10, 66, 51, 106, 240, 149, 73, 15, 45, 76, 108, 21, 200, 190, 63, 248, 7, 191, 134, 130, 163, 58, 114, 112, 192, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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