Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb0ffb7b024c6c19c2ceeabc9ec8a256e55f250af67737c3cb1fda9f174d40ed

Tx prefix hash: 60b0cb253d2f21fbb7f8959c5463628d7b6fc5e24d6429ccc01be0a6c6c766cc
Tx public key: 32a2a7bd8c03d4fc8bdb64182f3c883067868e67f1866db3fdaa593ccd7f44c1
Timestamp: 1722819859 Timestamp [UTC]: 2024-08-05 01:04:19 Age [y:d:h:m:s]: 02:101:12:35:16
Block: 1080925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597247 RingCT/type: yes/0
Extra: 0132a2a7bd8c03d4fc8bdb64182f3c883067868e67f1866db3fdaa593ccd7f44c102110000000be914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6b1054b9da06b682575c6d7c7d7adbc5aceb6a362ee756544ad32012f7cdfd25 0.000600000000 1554476 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": 1080935, "vin": [ { "gen": { "height": 1080925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b1054b9da06b682575c6d7c7d7adbc5aceb6a362ee756544ad32012f7cdfd25" } } ], "extra": [ 1, 50, 162, 167, 189, 140, 3, 212, 252, 139, 219, 100, 24, 47, 60, 136, 48, 103, 134, 142, 103, 241, 134, 109, 179, 253, 170, 89, 60, 205, 127, 68, 193, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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: