Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7898de98bfd01354d88a6417965d96f8a6e066fdb64357405a6f77e8d46dbba

Tx prefix hash: e16fa04875a44b80d4aa58b287a98c47329377f1f3ad520789a61aa099eb6539
Tx public key: cfe2101624187aa52e86627d559ca0a004f44d6059eeb714ced53e77e8f3030a
Timestamp: 1740266513 Timestamp [UTC]: 2025-02-22 23:21:53 Age [y:d:h:m:s]: 01:077:19:44:23
Block: 1225102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306436 RingCT/type: yes/0
Extra: 01cfe2101624187aa52e86627d559ca0a004f44d6059eeb714ced53e77e8f3030a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 61558ca36fd14acb15e3999ae6f16ebbfd9df8d1e8973d4c143ac24dfe57a44c 0.000600000000 1711967 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": 1225112, "vin": [ { "gen": { "height": 1225102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61558ca36fd14acb15e3999ae6f16ebbfd9df8d1e8973d4c143ac24dfe57a44c" } } ], "extra": [ 1, 207, 226, 16, 22, 36, 24, 122, 165, 46, 134, 98, 125, 85, 156, 160, 160, 4, 244, 77, 96, 89, 238, 183, 20, 206, 213, 62, 119, 232, 243, 3, 10, 2, 17, 0, 0, 0, 5, 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: