Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12dae2349bcd507287dcdb464ace1b9e5c7914c3bbe0b9bd73ac99a71cf00aa6

Tx prefix hash: 5ec8c9c7f8c273287deda86d2af63df19aff119295e4135f3b8b5d3c1642342d
Tx public key: 585b6a0ef385c2e3e8718a4fc9bbd3fa94c8a63e1eb0eb0f6fb0463d027ac4c4
Timestamp: 1742735535 Timestamp [UTC]: 2025-03-23 13:12:15 Age [y:d:h:m:s]: 01:050:01:37:50
Block: 1245567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286608 RingCT/type: yes/0
Extra: 01585b6a0ef385c2e3e8718a4fc9bbd3fa94c8a63e1eb0eb0f6fb0463d027ac4c4021100000008af845649000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8d4009d4b743c00b454fec521ec4544a3cde600ffc641b00e83131d053ec4776 0.000600000000 1732558 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": 1245577, "vin": [ { "gen": { "height": 1245567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d4009d4b743c00b454fec521ec4544a3cde600ffc641b00e83131d053ec4776" } } ], "extra": [ 1, 88, 91, 106, 14, 243, 133, 194, 227, 232, 113, 138, 79, 201, 187, 211, 250, 148, 200, 166, 62, 30, 176, 235, 15, 111, 176, 70, 61, 2, 122, 196, 196, 2, 17, 0, 0, 0, 8, 175, 132, 86, 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: