Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 161b0f9526f9609fa18f5da59ee9e95e6e4af810ec21095565cff9e6e19f1e48

Tx prefix hash: b005336ed77e5fd27db0d207bfc404c5c1ed0bc57ea44ce8a9d842392cfab3af
Tx public key: e3507a57f3af4e76067d12fb86890dc5a2d9eb8f3c0bd4f3712a12dde2232b77
Timestamp: 1635589381 Timestamp [UTC]: 2021-10-30 10:23:01 Age [y:d:h:m:s]: 04:196:05:40:52
Block: 363572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169380 RingCT/type: yes/0
Extra: 01e3507a57f3af4e76067d12fb86890dc5a2d9eb8f3c0bd4f3712a12dde2232b7702110000000c4f792ffd000000000000000000

1 output(s) for total of 0.038312054496 xmr

stealth address amount amount idx tag
00: f1c56f9ced173779788f75ac29d9db96eb28d67e24b84f39a12632ff2b3adb73 0.038312054496 738894 of 0 -

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": 363582, "vin": [ { "gen": { "height": 363572 } } ], "vout": [ { "amount": 38312054496, "target": { "key": "f1c56f9ced173779788f75ac29d9db96eb28d67e24b84f39a12632ff2b3adb73" } } ], "extra": [ 1, 227, 80, 122, 87, 243, 175, 78, 118, 6, 125, 18, 251, 134, 137, 13, 197, 162, 217, 235, 143, 60, 11, 212, 243, 113, 42, 18, 221, 226, 35, 43, 119, 2, 17, 0, 0, 0, 12, 79, 121, 47, 253, 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: