Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07fe0db712268d3fc5b466f32b5ec9d698f4af1c0658208909c40ccec38fa738

Tx prefix hash: 16e0f176375e0ccbce65064e3b3f4ce28c25e82822a829841b925d8ceb9af57d
Tx public key: b20140e0a99f4ce735fb9ed7d22de1036567021e6fe6f0828e6047df6a9bd3be
Timestamp: 1648640894 Timestamp [UTC]: 2022-03-30 11:48:14 Age [y:d:h:m:s]: 04:049:23:19:51
Block: 469556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1067055 RingCT/type: yes/0
Extra: 01b20140e0a99f4ce735fb9ed7d22de1036567021e6fe6f0828e6047df6a9bd3be02110000000bcb8520c2000000000000000000

1 output(s) for total of 0.017067358076 xmr

stealth address amount amount idx tag
00: dbee1106dfeb4e93457815b8db4a07cd62eea21fc1f7d832d206d0b1c05ff618 0.017067358076 888518 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": 469566, "vin": [ { "gen": { "height": 469556 } } ], "vout": [ { "amount": 17067358076, "target": { "key": "dbee1106dfeb4e93457815b8db4a07cd62eea21fc1f7d832d206d0b1c05ff618" } } ], "extra": [ 1, 178, 1, 64, 224, 169, 159, 76, 231, 53, 251, 158, 215, 210, 45, 225, 3, 101, 103, 2, 30, 111, 230, 240, 130, 142, 96, 71, 223, 106, 155, 211, 190, 2, 17, 0, 0, 0, 11, 203, 133, 32, 194, 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: