Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5397654b71f3168f5694903db020d00798e433b40f33a28014d60752fdb40f18

Tx prefix hash: a55c25fc86f03da0ea007ab405064db0c92011b3d3ffe5c91cdbc5b95eec6b88
Tx public key: 7c2cda6796320923dcef2c7c85b3f87bf7c1b0b9a7338806f09bb47c7177f15a
Timestamp: 1578437350 Timestamp [UTC]: 2020-01-07 22:49:10 Age [y:d:h:m:s]: 06:320:12:08:04
Block: 40826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1642668 RingCT/type: yes/0
Extra: 017c2cda6796320923dcef2c7c85b3f87bf7c1b0b9a7338806f09bb47c7177f15a02110000000c4943cd9f000000000000000000

1 output(s) for total of 0.449497582917 xmr

stealth address amount amount idx tag
00: 505f71efadaa2a7076e5c2f2a18887961d2780cc1c34c76088ed9ce6d908c9b1 0.449497582917 72080 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": 40836, "vin": [ { "gen": { "height": 40826 } } ], "vout": [ { "amount": 449497582917, "target": { "key": "505f71efadaa2a7076e5c2f2a18887961d2780cc1c34c76088ed9ce6d908c9b1" } } ], "extra": [ 1, 124, 44, 218, 103, 150, 50, 9, 35, 220, 239, 44, 124, 133, 179, 248, 123, 247, 193, 176, 185, 167, 51, 136, 6, 240, 155, 180, 124, 113, 119, 241, 90, 2, 17, 0, 0, 0, 12, 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: