Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b2296a5f96f7a9804f73ec1219cbc8b67f7e5dda80bf845e92cccaeb5114d3a

Tx prefix hash: 72106ed8f772f4be2a386f6a483431a5befc8eebd3a3f762ba5f42db83bb436e
Tx public key: 2dc59bd8b54f181cef60b1f21702cd4227546679771c9082b3eaf17cfeeb29e6
Timestamp: 1755468037 Timestamp [UTC]: 2025-08-17 22:00:37 Age [y:d:h:m:s]: 01:096:15:49:16
Block: 1348771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334723 RingCT/type: yes/0
Extra: 012dc59bd8b54f181cef60b1f21702cd4227546679771c9082b3eaf17cfeeb29e6021100000003b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bc021374b4dc6a57a6616ed43a88c54c204f15c02c75677c2f37dea9aaaca708 0.000600000000 1836700 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": 1348781, "vin": [ { "gen": { "height": 1348771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc021374b4dc6a57a6616ed43a88c54c204f15c02c75677c2f37dea9aaaca708" } } ], "extra": [ 1, 45, 197, 155, 216, 181, 79, 24, 28, 239, 96, 177, 242, 23, 2, 205, 66, 39, 84, 102, 121, 119, 28, 144, 130, 179, 234, 241, 124, 254, 235, 41, 230, 2, 17, 0, 0, 0, 3, 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: