Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe29f8d4b431a6ebe708f344a9b435c57e1f10dd373e451a9b84c8cf878354c

Tx prefix hash: afb0f2b0bfc23012521af19472589afa6ce509e471155db50c4415a53fb54ed0
Tx public key: 214aade07640348860ec2a3d89e11e871ac66d8bf17757dc2941b2e8022e545e
Timestamp: 1765351292 Timestamp [UTC]: 2025-12-10 07:21:32 Age [y:d:h:m:s]: 00:259:01:47:46
Block: 1430403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190904 RingCT/type: yes/0
Extra: 01214aade07640348860ec2a3d89e11e871ac66d8bf17757dc2941b2e8022e545e02110000000b70609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5d8b71b2730f43e69a60c8b6de1f10daa4c9790a637def5267a444049d7932f9 0.000600000000 1919152 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": 1430413, "vin": [ { "gen": { "height": 1430403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d8b71b2730f43e69a60c8b6de1f10daa4c9790a637def5267a444049d7932f9" } } ], "extra": [ 1, 33, 74, 173, 224, 118, 64, 52, 136, 96, 236, 42, 61, 137, 225, 30, 135, 26, 198, 109, 139, 241, 119, 87, 220, 41, 65, 178, 232, 2, 46, 84, 94, 2, 17, 0, 0, 0, 11, 112, 96, 157, 3, 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: