Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64ca4aa9789252bd11147bb258d720739eedbab100bfb70d5e1f0ae506b9b69a

Tx prefix hash: cc687b6f7028fa96e396e352db18ff6d67ae9b31210c9990aa1a6cf32d224aa3
Tx public key: 6650c2a0d1c780d617f3f6d8dd317807c1212061bf1c9df819372cb7414b7c55
Timestamp: 1734435358 Timestamp [UTC]: 2024-12-17 11:35:58 Age [y:d:h:m:s]: 01:144:20:37:34
Block: 1177140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354389 RingCT/type: yes/0
Extra: 016650c2a0d1c780d617f3f6d8dd317807c1212061bf1c9df819372cb7414b7c550211000000081f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3043eb5bfd7f1ede2d6fdc5e450e016223e2a815263c0e16dd970cf61bd7cdde 0.000600000000 1663505 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": 1177150, "vin": [ { "gen": { "height": 1177140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3043eb5bfd7f1ede2d6fdc5e450e016223e2a815263c0e16dd970cf61bd7cdde" } } ], "extra": [ 1, 102, 80, 194, 160, 209, 199, 128, 214, 23, 243, 246, 216, 221, 49, 120, 7, 193, 33, 32, 97, 191, 28, 157, 248, 25, 55, 44, 183, 65, 75, 124, 85, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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: