Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0db247569c6242d45efaf08bfaaf62f81594e1fb6054166c1f97845295dffbbf

Tx prefix hash: 166738001c0df618ed6247a4cd0aa1b2b54c8f7d81f798e4e8acd37059ad9a4b
Tx public key: 6883d817fa6dfaa04c73648ecebc0ecc77fd5104763d9d97f7e9005c3dd7114a
Timestamp: 1579797860 Timestamp [UTC]: 2020-01-23 16:44:20 Age [y:d:h:m:s]: 06:301:03:27:03
Block: 51521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1629839 RingCT/type: yes/0
Extra: 016883d817fa6dfaa04c73648ecebc0ecc77fd5104763d9d97f7e9005c3dd7114a021100000007391a8d0e000000000000000000

1 output(s) for total of 0.414276568586 xmr

stealth address amount amount idx tag
00: 4cb4f2ced92dedd548c4b0176af1c5b36a6ad56f20420a9d899c011026fd4f92 0.414276568586 95545 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": 51531, "vin": [ { "gen": { "height": 51521 } } ], "vout": [ { "amount": 414276568586, "target": { "key": "4cb4f2ced92dedd548c4b0176af1c5b36a6ad56f20420a9d899c011026fd4f92" } } ], "extra": [ 1, 104, 131, 216, 23, 250, 109, 250, 160, 76, 115, 100, 142, 206, 188, 14, 204, 119, 253, 81, 4, 118, 61, 157, 151, 247, 233, 0, 92, 61, 215, 17, 74, 2, 17, 0, 0, 0, 7, 57, 26, 141, 14, 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: