Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 591e23163519b1786b98aab23ed1ac4b0ffe56dfda5e90c8895176bcbb2e57a3

Tx prefix hash: 70f2dbe6f673c8b63dc5a0227b8dba1e1352fad6f05d9931a3e8a01084100eac
Tx public key: 5875971860689b9ceddf0081aee52a73d2a671118c3f5592f3e63d01834f1cdd
Timestamp: 1602481291 Timestamp [UTC]: 2020-10-12 05:41:31 Age [y:d:h:m:s]: 06:041:12:55:13
Block: 140780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1542714 RingCT/type: yes/0
Extra: 015875971860689b9ceddf0081aee52a73d2a671118c3f5592f3e63d01834f1cdd0211000002e53a3a2186000000000000000000

1 output(s) for total of 0.209670882754 xmr

stealth address amount amount idx tag
00: 13d0e1c3c6e4c69d9d12e568806aa03034721099d0539cd660f6f0b9ac21dce2 0.209670882754 233799 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": 140790, "vin": [ { "gen": { "height": 140780 } } ], "vout": [ { "amount": 209670882754, "target": { "key": "13d0e1c3c6e4c69d9d12e568806aa03034721099d0539cd660f6f0b9ac21dce2" } } ], "extra": [ 1, 88, 117, 151, 24, 96, 104, 155, 156, 237, 223, 0, 129, 174, 229, 42, 115, 210, 166, 113, 17, 140, 63, 85, 146, 243, 230, 61, 1, 131, 79, 28, 221, 2, 17, 0, 0, 2, 229, 58, 58, 33, 134, 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: