Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f1621d7e7d7265ef4949e6f720ca63bc3b2ac63d7a4896be1e158ac7575ad69

Tx prefix hash: d28901e9ae17544a9010a70cfd3dcf7282e79a9533df97091e1f8ef65f42a69c
Tx public key: ad67c5b7b1f55dcf11fd9acfe0595011e88d9f2cfd087f30bfcf9608205d02c3
Timestamp: 1649321813 Timestamp [UTC]: 2022-04-07 08:56:53 Age [y:d:h:m:s]: 04:229:10:15:58
Block: 475023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1208471 RingCT/type: yes/0
Extra: 01ad67c5b7b1f55dcf11fd9acfe0595011e88d9f2cfd087f30bfcf9608205d02c3021100000001a8c141c5000000000000000000

1 output(s) for total of 0.016370119574 xmr

stealth address amount amount idx tag
00: 900fbedf05533b2d08003bc0c4f1a721574c5e3f7a31a08bd9d613013586956f 0.016370119574 895188 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": 475033, "vin": [ { "gen": { "height": 475023 } } ], "vout": [ { "amount": 16370119574, "target": { "key": "900fbedf05533b2d08003bc0c4f1a721574c5e3f7a31a08bd9d613013586956f" } } ], "extra": [ 1, 173, 103, 197, 183, 177, 245, 93, 207, 17, 253, 154, 207, 224, 89, 80, 17, 232, 141, 159, 44, 253, 8, 127, 48, 191, 207, 150, 8, 32, 93, 2, 195, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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: