Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34f1bc48660715640e0371c0085241da816ba01f7340ef79542bedfb2bbf11fa

Tx prefix hash: 83656a57123e09922c36999ebeea89b8db3b7607402b07e9c55c50c4dfb8e2c5
Tx public key: 2cf3064dc28b42a6e78d315643563bba944de1a9f8ccb6226a063f633fa96c4a
Timestamp: 1755618449 Timestamp [UTC]: 2025-08-19 15:47:29 Age [y:d:h:m:s]: 01:091:12:44:17
Block: 1349966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331668 RingCT/type: yes/0
Extra: 012cf3064dc28b42a6e78d315643563bba944de1a9f8ccb6226a063f633fa96c4a021100000009b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a58c97a89b17704eb6697e2e031ca9359eea36b58c19e6719ce4de72e4259b27 0.000600000000 1837905 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": 1349976, "vin": [ { "gen": { "height": 1349966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a58c97a89b17704eb6697e2e031ca9359eea36b58c19e6719ce4de72e4259b27" } } ], "extra": [ 1, 44, 243, 6, 77, 194, 139, 66, 166, 231, 141, 49, 86, 67, 86, 59, 186, 148, 77, 225, 169, 248, 204, 182, 34, 106, 6, 63, 99, 63, 169, 108, 74, 2, 17, 0, 0, 0, 9, 178, 247, 132, 196, 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: