Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc66d666c1b333337925ab30e8d4f219b5ae071bba7fbc08a468a74a23bcfb99

Tx prefix hash: ddcc8aadaf12f663af08280b58d9af7c5b5e6b88fc6b758db5b88074886955ef
Tx public key: f5ff68d82a8e44d08b5aabb3bd2223c728dd722527eb78de44e31953f8e5aa5a
Timestamp: 1770149189 Timestamp [UTC]: 2026-02-03 20:06:29 Age [y:d:h:m:s]: 00:287:13:54:39
Block: 1470014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211039 RingCT/type: yes/0
Extra: 01f5ff68d82a8e44d08b5aabb3bd2223c728dd722527eb78de44e31953f8e5aa5a021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 46329ac16aaffe48a9aeea6a2c9e75f54f3527dca1ac209d9af009b14bcd1a1f 0.000600000000 1959280 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": 1470024, "vin": [ { "gen": { "height": 1470014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46329ac16aaffe48a9aeea6a2c9e75f54f3527dca1ac209d9af009b14bcd1a1f" } } ], "extra": [ 1, 245, 255, 104, 216, 42, 142, 68, 208, 139, 90, 171, 179, 189, 34, 35, 199, 40, 221, 114, 37, 39, 235, 120, 222, 68, 227, 25, 83, 248, 229, 170, 90, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: