Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48d36e7d7e3c66cc289e9a2f814005353af03e118f34dcfd14f436d95c28579d

Tx prefix hash: 462dcc30445b2402e9064b58136fe62ed261007ea405a91d961bf22bf2d69f36
Tx public key: 5665b3e2d98cf5e8b134987cf3d098bdb9ea7eac5bd963a9cb7eb260f42ec9dc
Timestamp: 1732765681 Timestamp [UTC]: 2024-11-28 03:48:01 Age [y:d:h:m:s]: 01:358:05:56:22
Block: 1163289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520035 RingCT/type: yes/0
Extra: 015665b3e2d98cf5e8b134987cf3d098bdb9ea7eac5bd963a9cb7eb260f42ec9dc0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fd6ef9c193544159404832c13bfe8beb7916fe4143f0ab60d7fd1960deed7efc 0.000600000000 1648956 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 dinastycoin-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": 1163299, "vin": [ { "gen": { "height": 1163289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd6ef9c193544159404832c13bfe8beb7916fe4143f0ab60d7fd1960deed7efc" } } ], "extra": [ 1, 86, 101, 179, 226, 217, 140, 245, 232, 177, 52, 152, 124, 243, 208, 152, 189, 185, 234, 126, 172, 91, 217, 99, 169, 203, 126, 178, 96, 244, 46, 201, 220, 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): devel-2026-02-02-6303d2a (1.2) | monero version: