Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d44d39065a0bc75fe7fcd6f76e99a301e0581ad5c59298bcf1772cd8d017af3

Tx prefix hash: 1cd9b21b74444f4ea992ff948d4c2358bb9b73aafc6d8b7c6675e77080e33604
Tx public key: 1e792a960714a036e32b2f0778045e90daa2a5df3f559fa97861c1bb4bc228d9
Timestamp: 1747788937 Timestamp [UTC]: 2025-05-21 00:55:37 Age [y:d:h:m:s]: 01:184:23:30:47
Block: 1287409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396085 RingCT/type: yes/0
Extra: 011e792a960714a036e32b2f0778045e90daa2a5df3f559fa97861c1bb4bc228d90211000000041f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1c6d348f5e7d408e3d7f9040cb4cb88aeff267590f0f51cd775f54e1d3e09da8 0.000600000000 1774876 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": 1287419, "vin": [ { "gen": { "height": 1287409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c6d348f5e7d408e3d7f9040cb4cb88aeff267590f0f51cd775f54e1d3e09da8" } } ], "extra": [ 1, 30, 121, 42, 150, 7, 20, 160, 54, 227, 43, 47, 7, 120, 4, 94, 144, 218, 162, 165, 223, 63, 85, 159, 169, 120, 97, 193, 187, 75, 194, 40, 217, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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: