Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0174c05186fafb22ad69751b43a83fcafc77b43d7eaef836ba160d7c7fb49e3c

Tx prefix hash: 1521a59184915deda6fecc39b71a6edfe36da69b1a7b8a91db1d75b8de8f5047
Tx public key: a0c444100dae30d68b7ea6ab476d47f128f4b06055fe79c30136232e51f44907
Timestamp: 1744425615 Timestamp [UTC]: 2025-04-12 02:40:15 Age [y:d:h:m:s]: 01:034:12:14:34
Block: 1259556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275614 RingCT/type: yes/0
Extra: 01a0c444100dae30d68b7ea6ab476d47f128f4b06055fe79c30136232e51f44907021100000006dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a27d4c131737a85c32a0250c8551041c24b6a98231e54d602b99e8c2585420b8 0.000600000000 1746703 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": 1259566, "vin": [ { "gen": { "height": 1259556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a27d4c131737a85c32a0250c8551041c24b6a98231e54d602b99e8c2585420b8" } } ], "extra": [ 1, 160, 196, 68, 16, 13, 174, 48, 214, 139, 126, 166, 171, 71, 109, 71, 241, 40, 244, 176, 96, 85, 254, 121, 195, 1, 54, 35, 46, 81, 244, 73, 7, 2, 17, 0, 0, 0, 6, 219, 181, 113, 193, 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: