Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66da2dec5f4dd6029cf3555b1cbc9d5c576bb337ddef289e6ac43aa9ad84a01d

Tx prefix hash: 1fa967a78ccf5a05e91657f69d34bfd13f4611bd90c4fc3f97f788763136a7e2
Tx public key: cc4fe86e31b973ab57f8a8a39d1253d94d1168270d8b407399155d5840db7875
Timestamp: 1774782779 Timestamp [UTC]: 2026-03-29 11:12:59 Age [y:d:h:m:s]: 00:234:06:07:34
Block: 1508325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172948 RingCT/type: yes/0
Extra: 01cc4fe86e31b973ab57f8a8a39d1253d94d1168270d8b407399155d5840db7875021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 38bbb5140915e3b6ad87385bad1239cb14b1b0ad92d262e929f7078bb2771068 0.000600000000 1998077 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": 1508335, "vin": [ { "gen": { "height": 1508325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38bbb5140915e3b6ad87385bad1239cb14b1b0ad92d262e929f7078bb2771068" } } ], "extra": [ 1, 204, 79, 232, 110, 49, 185, 115, 171, 87, 248, 168, 163, 157, 18, 83, 217, 77, 17, 104, 39, 13, 139, 64, 115, 153, 21, 93, 88, 64, 219, 120, 117, 2, 17, 0, 0, 0, 3, 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: