Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01b044dfdb82f961dca4f00a9f5fb7108553ff6a7dd756af5cde16a3e605dc42

Tx prefix hash: 7e2bf4ce1b1aa93e5be621aea2781279bd68582318e380b1d7e110b0492eb8ac
Tx public key: 8b0907c522f742be05221a8b47fbcbf981d974093e2a4daa2b841de4681a52b2
Timestamp: 1771532333 Timestamp [UTC]: 2026-02-19 20:18:53 Age [y:d:h:m:s]: 00:270:00:35:31
Block: 1481433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198460 RingCT/type: yes/0
Extra: 018b0907c522f742be05221a8b47fbcbf981d974093e2a4daa2b841de4681a52b2021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aac4e0ae80a724e6bd54b0d2bea448d554ab760c30d3c2d709f5852d85d6c8d1 0.000600000000 1970811 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": 1481443, "vin": [ { "gen": { "height": 1481433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aac4e0ae80a724e6bd54b0d2bea448d554ab760c30d3c2d709f5852d85d6c8d1" } } ], "extra": [ 1, 139, 9, 7, 197, 34, 247, 66, 190, 5, 34, 26, 139, 71, 251, 203, 249, 129, 217, 116, 9, 62, 42, 77, 170, 43, 132, 29, 228, 104, 26, 82, 178, 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: