Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f0ec3ab78b0dd44fa901867c2caf7073f46da16fe2127c7cba2ad7a1104ca91

Tx prefix hash: 1e0f69dc994a31cbf5753330b2a0679592021e18263a81e5e23e6322b4a18fb6
Tx public key: 4fec18bfd2be89560a5d36b9981dd0b2eac0a89aa49fdea07b6b840ae87ac4db
Timestamp: 1641065406 Timestamp [UTC]: 2022-01-01 19:30:06 Age [y:d:h:m:s]: 04:134:13:58:32
Block: 408361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1125918 RingCT/type: yes/0
Extra: 014fec18bfd2be89560a5d36b9981dd0b2eac0a89aa49fdea07b6b840ae87ac4db0211000000014a0f5013000000000000000000

1 output(s) for total of 0.027223446826 xmr

stealth address amount amount idx tag
00: 30f2d8a684e9d7f3f763894e0ce11ffa1dc52ab7753def1dc7a52fecbd6fe64c 0.027223446826 810364 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": 408371, "vin": [ { "gen": { "height": 408361 } } ], "vout": [ { "amount": 27223446826, "target": { "key": "30f2d8a684e9d7f3f763894e0ce11ffa1dc52ab7753def1dc7a52fecbd6fe64c" } } ], "extra": [ 1, 79, 236, 24, 191, 210, 190, 137, 86, 10, 93, 54, 185, 152, 29, 208, 178, 234, 192, 168, 154, 164, 159, 222, 160, 123, 107, 132, 10, 232, 122, 196, 219, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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: