Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd2bc682de35ddf9129d82037a0e15762717b46eb4c4d593df733fa56300af4c

Tx prefix hash: 33e313ffe60fb053c72707e186cd0b0b96c52da9e8d1d3437fd22c19e2121601
Tx public key: ebb216d4917d9af0fe4772bde9bc5d6c16f12add70f10f938ee38437628b15e7
Timestamp: 1577619740 Timestamp [UTC]: 2019-12-29 11:42:20 Age [y:d:h:m:s]: 06:329:10:45:07
Block: 34328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1649166 RingCT/type: yes/0
Extra: 01ebb216d4917d9af0fe4772bde9bc5d6c16f12add70f10f938ee38437628b15e70211000000038a2ee0d9000000000000000000

1 output(s) for total of 0.472343498239 xmr

stealth address amount amount idx tag
00: 8272bbb62e221cd3b771242569e3e36da3b070ae443eca59cb4c9738153b984b 0.472343498239 57743 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": 34338, "vin": [ { "gen": { "height": 34328 } } ], "vout": [ { "amount": 472343498239, "target": { "key": "8272bbb62e221cd3b771242569e3e36da3b070ae443eca59cb4c9738153b984b" } } ], "extra": [ 1, 235, 178, 22, 212, 145, 125, 154, 240, 254, 71, 114, 189, 233, 188, 93, 108, 22, 241, 42, 221, 112, 241, 15, 147, 142, 227, 132, 55, 98, 139, 21, 231, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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: