Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47e2364d55a3174882ff7f332465b078015aa7b200f7e4d1f80408c4d6704a7f

Tx prefix hash: 61ade595ec7bc1f3406185ccdd7e973b0b1a8fdfa2b150c8af16f0e57587dc13
Tx public key: 82f06be0bc6d8826f826e35156775ca2689bd39faba1ee73b31dc798d73bdd4a
Timestamp: 1727666863 Timestamp [UCT]: 2024-09-30 03:27:43 Age [y:d:h:m:s]: 01:039:09:30:50
Block: 1121125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286537 RingCT/type: yes/0
Extra: 0182f06be0bc6d8826f826e35156775ca2689bd39faba1ee73b31dc798d73bdd4a02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03db9f5af6f78a2b5d15de89793fa2e79d96e737eb12c07914cbd84a29591c7b 0.600000000000 1603284 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": 1121135, "vin": [ { "gen": { "height": 1121125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03db9f5af6f78a2b5d15de89793fa2e79d96e737eb12c07914cbd84a29591c7b" } } ], "extra": [ 1, 130, 240, 107, 224, 188, 109, 136, 38, 248, 38, 227, 81, 86, 119, 92, 162, 104, 155, 211, 159, 171, 161, 238, 115, 179, 29, 199, 152, 215, 59, 221, 74, 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