Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 816b16387a879b6c118643b20a2bc2ca4defa358798cccbe56cbeaf9a3695cf4

Tx prefix hash: b9adeb5c61b5f5924db3326f8d3ef09d15b045901086983c0bcf5031b1c3396e
Tx public key: dc40cae2854e200b452b663d522dcd99ca5ddd780d93f6af3febfb036d5dcfa0
Timestamp: 1638644523 Timestamp [UTC]: 2021-12-04 19:02:03 Age [y:d:h:m:s]: 04:353:01:18:20
Block: 388426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1295068 RingCT/type: yes/0
Extra: 01dc40cae2854e200b452b663d522dcd99ca5ddd780d93f6af3febfb036d5dcfa0021100000001a8a4bccb000000000000000000

1 output(s) for total of 0.031694491401 xmr

stealth address amount amount idx tag
00: a02d61a54a5d0066aa0d2810f3d7e7f84e43a9d10700b26b55783a69c79a0dc0 0.031694491401 783061 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": 388436, "vin": [ { "gen": { "height": 388426 } } ], "vout": [ { "amount": 31694491401, "target": { "key": "a02d61a54a5d0066aa0d2810f3d7e7f84e43a9d10700b26b55783a69c79a0dc0" } } ], "extra": [ 1, 220, 64, 202, 226, 133, 78, 32, 11, 69, 43, 102, 61, 82, 45, 205, 153, 202, 93, 221, 120, 13, 147, 246, 175, 63, 235, 251, 3, 109, 93, 207, 160, 2, 17, 0, 0, 0, 1, 168, 164, 188, 203, 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: