Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0795fcbd3ae2dac3c520e10a23129bc4ae37e967cbcf15511682e4bd8f93999

Tx prefix hash: 522c1240ededc582261a2bd4cd8267db142ddf7b330033bf9c301a8f94ced02e
Tx public key: d79d6bcb8a959b942b5d3e9b438d56c8fca417c0324634a89d30899511087add
Timestamp: 1648215211 Timestamp [UTC]: 2022-03-25 13:33:31 Age [y:d:h:m:s]: 04:048:08:27:59
Block: 466107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1065530 RingCT/type: yes/0
Extra: 01d79d6bcb8a959b942b5d3e9b438d56c8fca417c0324634a89d30899511087add021100000003d3fcec30000000000000000000

1 output(s) for total of 0.017522427589 xmr

stealth address amount amount idx tag
00: fb8e3de9dd859e1c7b5f9dbca33b6c0c5664a5a14f2a257c250111cd3c4b8e9d 0.017522427589 884348 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": 466117, "vin": [ { "gen": { "height": 466107 } } ], "vout": [ { "amount": 17522427589, "target": { "key": "fb8e3de9dd859e1c7b5f9dbca33b6c0c5664a5a14f2a257c250111cd3c4b8e9d" } } ], "extra": [ 1, 215, 157, 107, 203, 138, 149, 155, 148, 43, 93, 62, 155, 67, 141, 86, 200, 252, 164, 23, 192, 50, 70, 52, 168, 157, 48, 137, 149, 17, 8, 122, 221, 2, 17, 0, 0, 0, 3, 211, 252, 236, 48, 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: