Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b4f071b69872d0d89fbdf71917ed9169c898e172cc72f27b2255ec818d86d68

Tx prefix hash: 6fec9021f0125dd43f1acf8d4075cc7c603226ac329555f033e265f37d28e200
Tx public key: 0700cddce031cd64f780ca0d1dfe21d1c500ed7ea59db9e8470e3e683ee77668
Timestamp: 1577144232 Timestamp [UTC]: 2019-12-23 23:37:12 Age [y:d:h:m:s]: 06:143:09:45:55
Block: 30191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1503309 RingCT/type: yes/0
Extra: 010700cddce031cd64f780ca0d1dfe21d1c500ed7ea59db9e8470e3e683ee77668021100000012d81c26c0000000000000000000

1 output(s) for total of 0.487489814550 xmr

stealth address amount amount idx tag
00: 696f498310398f9c424c4f2bc53e570b663079f59c440b751b99aa82460490ca 0.487489814550 49855 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": 30201, "vin": [ { "gen": { "height": 30191 } } ], "vout": [ { "amount": 487489814550, "target": { "key": "696f498310398f9c424c4f2bc53e570b663079f59c440b751b99aa82460490ca" } } ], "extra": [ 1, 7, 0, 205, 220, 224, 49, 205, 100, 247, 128, 202, 13, 29, 254, 33, 209, 197, 0, 237, 126, 165, 157, 185, 232, 71, 14, 62, 104, 62, 231, 118, 104, 2, 17, 0, 0, 0, 18, 216, 28, 38, 192, 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: