Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21015696a4e84b8eedb0718fe578214c5d3814f86ee0b2d01c084bff57ccc9d1

Tx prefix hash: c2e69bd7ca9b95aa9e5bbcbc14fc25067dc4e62e23294fc9f2f7f01b28276602
Tx public key: 06fb74d74fed1be3f7d4fe17ec4c693bb43baefb21dffc0260c72c78aaf7ddff
Timestamp: 1705589791 Timestamp [UTC]: 2024-01-18 14:56:31 Age [y:d:h:m:s]: 02:308:11:34:03
Block: 938069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745425 RingCT/type: yes/0
Extra: 0106fb74d74fed1be3f7d4fe17ec4c693bb43baefb21dffc0260c72c78aaf7ddff0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 859edc0a79c0c92d014bf46ca9bd0dc6fae8fafd4c05e519be55d919be03ee1b 0.000600000000 1396133 of 15 -

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": 938079, "vin": [ { "gen": { "height": 938069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "859edc0a79c0c92d014bf46ca9bd0dc6fae8fafd4c05e519be55d919be03ee1b" } } ], "extra": [ 1, 6, 251, 116, 215, 79, 237, 27, 227, 247, 212, 254, 23, 236, 76, 105, 59, 180, 59, 174, 251, 33, 223, 252, 2, 96, 199, 44, 120, 170, 247, 221, 255, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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: