Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa88c92988d9f2fac1264636652b227828353e04a5137bdf74ef88ee5ab75f82

Tx prefix hash: a0109914f62858e3588675ef735e552c66355ba9194afd869e76117ac4eedc2b
Tx public key: 9a5773b4924df8d0387e051b8aa6152860e6a2cb24fe33f0dd7efe83a44070e2
Timestamp: 1729993333 Timestamp [UTC]: 2024-10-27 01:42:13 Age [y:d:h:m:s]: 02:025:23:57:57
Block: 1140376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543118 RingCT/type: yes/0
Extra: 019a5773b4924df8d0387e051b8aa6152860e6a2cb24fe33f0dd7efe83a44070e2021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0770f5d24b5126def89e908942c10b09c8007782a99f63c7f97701f7477292dc 0.000600000000 1624171 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": 1140386, "vin": [ { "gen": { "height": 1140376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0770f5d24b5126def89e908942c10b09c8007782a99f63c7f97701f7477292dc" } } ], "extra": [ 1, 154, 87, 115, 180, 146, 77, 248, 208, 56, 126, 5, 27, 138, 166, 21, 40, 96, 230, 162, 203, 36, 254, 51, 240, 221, 126, 254, 131, 164, 64, 112, 226, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: