Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dc3a4ed21460d4a18d7dd6f5483ef8e96e33efd55f5565c694b5ddb0f158c0a

Tx prefix hash: 0080facbdb77ebb0d0b4a9fbc1be5259792f4aff17fdf21f407d21daf73d6d3f
Tx public key: 377240feabf623750d0e7f0d301b063eaf4340fbce2ab9b4aa23c70ef5a420a5
Timestamp: 1650843887 Timestamp [UTC]: 2022-04-24 23:44:47 Age [y:d:h:m:s]: 04:209:08:45:33
Block: 487435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1194320 RingCT/type: yes/0
Extra: 01377240feabf623750d0e7f0d301b063eaf4340fbce2ab9b4aa23c70ef5a420a5021100000006faf35c9c000000000000000000

1 output(s) for total of 0.014891063823 xmr

stealth address amount amount idx tag
00: 04bad83fc3557d258c63498715b0b846ada22f1a9b7be23e30458e079167ffdf 0.014891063823 909904 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": 487445, "vin": [ { "gen": { "height": 487435 } } ], "vout": [ { "amount": 14891063823, "target": { "key": "04bad83fc3557d258c63498715b0b846ada22f1a9b7be23e30458e079167ffdf" } } ], "extra": [ 1, 55, 114, 64, 254, 171, 246, 35, 117, 13, 14, 127, 13, 48, 27, 6, 62, 175, 67, 64, 251, 206, 42, 185, 180, 170, 35, 199, 14, 245, 164, 32, 165, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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: