Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 561ea3f9713564f2a07fa4b1bf29a7a16e775d930e486b5cefcff2a3cec7d0c9

Tx prefix hash: 57ccdb5e771549c5e22da504ad41c90cfc36782ec509920e0f21a2a595588f15
Tx public key: bccd9d6c3d33b940c7486cc64cf07bdd15d075dd8f6e9be9ad3af46423738699
Timestamp: 1768094361 Timestamp [UTC]: 2026-01-11 01:19:21 Age [y:d:h:m:s]: 00:287:08:57:32
Block: 1453144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 208963 RingCT/type: yes/0
Extra: 01bccd9d6c3d33b940c7486cc64cf07bdd15d075dd8f6e9be9ad3af464237386990209000000058970985800

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a61478c685163942f48430c5f0bb2af58f33659c475721bd945836af39eceda 0.000600000000 1942188 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": 1453154, "vin": [ { "gen": { "height": 1453144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a61478c685163942f48430c5f0bb2af58f33659c475721bd945836af39eceda" } } ], "extra": [ 1, 188, 205, 157, 108, 61, 51, 185, 64, 199, 72, 108, 198, 76, 240, 123, 221, 21, 208, 117, 221, 143, 110, 155, 233, 173, 58, 244, 100, 35, 115, 134, 153, 2, 9, 0, 0, 0, 5, 137, 112, 152, 88, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: