Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bc547d24bf0d03d6df03ca171666867d7ecd9bdf6dd58474285b31973bc04eb

Tx prefix hash: 1b552044da52f6185870000ccd99d6acf9ab3878d32795911d89d4c7dc180daa
Tx public key: 159045e59280c7b37d9798f8ebea1798a353040e5d0de0f5d2ba0927dbf7c54b
Timestamp: 1774805904 Timestamp [UTC]: 2026-03-29 17:38:24 Age [y:d:h:m:s]: 00:234:23:49:53
Block: 1508514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173526 RingCT/type: yes/0
Extra: 01159045e59280c7b37d9798f8ebea1798a353040e5d0de0f5d2ba0927dbf7c54b021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 965986e7240ab865bf488e65f7a4020a3e6ebb246ad3f4418bb337a2282ce4fb 0.000600000000 1998266 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": 1508524, "vin": [ { "gen": { "height": 1508514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "965986e7240ab865bf488e65f7a4020a3e6ebb246ad3f4418bb337a2282ce4fb" } } ], "extra": [ 1, 21, 144, 69, 229, 146, 128, 199, 179, 125, 151, 152, 248, 235, 234, 23, 152, 163, 83, 4, 14, 93, 13, 224, 245, 210, 186, 9, 39, 219, 247, 197, 75, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: