Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ac82f9da7f7f4e61d69d77272531666a69b695df389bc35982e6c3e30c8007b

Tx prefix hash: 9f6958d8e5a1575ecfacec7b5d43bbc4f2a15aa359569859355953937d978cc8
Tx public key: 334f92b6b52ba6e74a440f0421e510d7134f8d7bbe15dbcab5053f5903eb346c
Timestamp: 1722450848 Timestamp [UCT]: 2024-07-31 18:34:08 Age [y:d:h:m:s]: 01:069:14:30:51
Block: 1077866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308191 RingCT/type: yes/0
Extra: 01334f92b6b52ba6e74a440f0421e510d7134f8d7bbe15dbcab5053f5903eb346c02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c15afa316be0c908bf7b535e1a90b05d6ba63a40e1661a9da02b249780412187 0.600000000000 1550421 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 dinasty-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": 1077876, "vin": [ { "gen": { "height": 1077866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c15afa316be0c908bf7b535e1a90b05d6ba63a40e1661a9da02b249780412187" } } ], "extra": [ 1, 51, 79, 146, 182, 181, 43, 166, 231, 74, 68, 15, 4, 33, 229, 16, 215, 19, 79, 141, 123, 190, 21, 219, 202, 181, 5, 63, 89, 3, 235, 52, 108, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8