Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 718f9a26edaccd874b6d5c15085597ace24481d57230532aae4b50b0c9ca8f7b

Tx prefix hash: c08c49f1c54a525192f1aa6f3a4c617a0409321b7091a3d316e009b1f7207540
Tx public key: 6198c0ae0a6543865151fa24bad58261fe9ecfd6d370cf9d8a7b16b9363da96e
Timestamp: 1582055692 Timestamp [UTC]: 2020-02-18 19:54:52 Age [y:d:h:m:s]: 06:278:07:41:03
Block: 67716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1615778 RingCT/type: yes/0
Extra: 016198c0ae0a6543865151fa24bad58261fe9ecfd6d370cf9d8a7b16b9363da96e0211000000084943cd9f000000000000000000

1 output(s) for total of 0.366125172053 xmr

stealth address amount amount idx tag
00: 4c455e3bc6713ccf1d5e151cc7d143347a2201f6a16a201bffb772ab8c146d31 0.366125172053 124715 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": 67726, "vin": [ { "gen": { "height": 67716 } } ], "vout": [ { "amount": 366125172053, "target": { "key": "4c455e3bc6713ccf1d5e151cc7d143347a2201f6a16a201bffb772ab8c146d31" } } ], "extra": [ 1, 97, 152, 192, 174, 10, 101, 67, 134, 81, 81, 250, 36, 186, 213, 130, 97, 254, 158, 207, 214, 211, 112, 207, 157, 138, 123, 22, 185, 54, 61, 169, 110, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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: