Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c50f82df7add0e8cc59465be0a0c01e3f5518f35f548daf0ff75ec99afc5f511

Tx prefix hash: 606c7391acf3028cce5b5999d870117b4aed62e4836d17c3d697a1a77e91eb8d
Tx public key: 0d2a0f2ff7ff444fe845c5507ebcec4bdf76258d4af8ce5188e04da3e5e2dca2
Timestamp: 1757289596 Timestamp [UTC]: 2025-09-07 23:59:56 Age [y:d:h:m:s]: 01:071:22:33:55
Block: 1363693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317746 RingCT/type: yes/0
Extra: 010d2a0f2ff7ff444fe845c5507ebcec4bdf76258d4af8ce5188e04da3e5e2dca2021100000003b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2ec8605f8561c2334231c54dd2f5dcf97786f647e39d6fe905d72e2a8373c771 0.000600000000 1851732 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": 1363703, "vin": [ { "gen": { "height": 1363693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ec8605f8561c2334231c54dd2f5dcf97786f647e39d6fe905d72e2a8373c771" } } ], "extra": [ 1, 13, 42, 15, 47, 247, 255, 68, 79, 232, 69, 197, 80, 126, 188, 236, 75, 223, 118, 37, 141, 74, 248, 206, 81, 136, 224, 77, 163, 229, 226, 220, 162, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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: