Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a01eaaaf9b7676f35eb56893fd31ddf0baefb6bb6b4dbcb0bf746180034818cc

Tx prefix hash: 74c05c674e70d62b19f2932f7473a7cd1057427c3291b2c334457ce64baecc90
Tx public key: 0665bb956391752aa784a5a0454ced7a57f1dd6b7ab4f858c7d935b41c601165
Timestamp: 1742933834 Timestamp [UTC]: 2025-03-25 20:17:14 Age [y:d:h:m:s]: 01:045:05:53:54
Block: 1247195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283575 RingCT/type: yes/0
Extra: 010665bb956391752aa784a5a0454ced7a57f1dd6b7ab4f858c7d935b41c601165021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 44331d34402f929d19b3dae3a3b4969a3387721c71d31b55ef7fa71607a00da6 0.000600000000 1734196 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": 1247205, "vin": [ { "gen": { "height": 1247195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44331d34402f929d19b3dae3a3b4969a3387721c71d31b55ef7fa71607a00da6" } } ], "extra": [ 1, 6, 101, 187, 149, 99, 145, 117, 42, 167, 132, 165, 160, 69, 76, 237, 122, 87, 241, 221, 107, 122, 180, 248, 88, 199, 217, 53, 180, 28, 96, 17, 101, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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: