Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 878323de96fd51213751bcfc4e1676a45962f39e6d7a72c3fafffcc20a0e3774

Tx prefix hash: 6a63bbcee3c7c8f0d424de130c5424788b08c609d207a0fbbe621abe31c13a38
Tx public key: 1d281ac9f3f1ead5361739c2e956e447d98d170b32b3aa595e7b0d056884692b
Timestamp: 1772618938 Timestamp [UTC]: 2026-03-04 10:08:58 Age [y:d:h:m:s]: 00:254:15:38:50
Block: 1490425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187376 RingCT/type: yes/0
Extra: 011d281ac9f3f1ead5361739c2e956e447d98d170b32b3aa595e7b0d056884692b02110000000ae4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cd559a863e823a3f1364d26b6ca58c704e028bc65c5392c0aede1d7adbf4863a 0.000600000000 1979927 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": 1490435, "vin": [ { "gen": { "height": 1490425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd559a863e823a3f1364d26b6ca58c704e028bc65c5392c0aede1d7adbf4863a" } } ], "extra": [ 1, 29, 40, 26, 201, 243, 241, 234, 213, 54, 23, 57, 194, 233, 86, 228, 71, 217, 141, 23, 11, 50, 179, 170, 89, 94, 123, 13, 5, 104, 132, 105, 43, 2, 17, 0, 0, 0, 10, 228, 245, 25, 63, 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: