Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a74a21f9bb845ca6d5a74bd798ee028a00604c814b439d8d894ad4a8c1fbd231

Tx prefix hash: fd9178eb78839589d2b9d325b17c6cdcd9fbec70f4d14f4ce717f66a5bc71aad
Tx public key: e6032127c16ffd0617784ffeac3de9a9708dbf625285847e11179e611a4ede57
Timestamp: 1696662685 Timestamp [UTC]: 2023-10-07 07:11:25 Age [y:d:h:m:s]: 03:043:21:29:58
Block: 864279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 817359 RingCT/type: yes/0
Extra: 01e6032127c16ffd0617784ffeac3de9a9708dbf625285847e11179e611a4ede5702110000000475e3f0e9000000000000000000

1 output(s) for total of 0.000840010915 xmr

stealth address amount amount idx tag
00: c8cde87d35f6e0ed63ba0c37eef503d3d29747b81e73ac074e969bca30a06fa1 0.000840010915 1318789 of 0 -

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": 864289, "vin": [ { "gen": { "height": 864279 } } ], "vout": [ { "amount": 840010915, "target": { "key": "c8cde87d35f6e0ed63ba0c37eef503d3d29747b81e73ac074e969bca30a06fa1" } } ], "extra": [ 1, 230, 3, 33, 39, 193, 111, 253, 6, 23, 120, 79, 254, 172, 61, 233, 169, 112, 141, 191, 98, 82, 133, 132, 126, 17, 23, 158, 97, 26, 78, 222, 87, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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: