Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a8fec237c2495f3aee2bb6adafb4af3395654056fdb9aa8dc920e47d800e820

Tx prefix hash: 18f0979e25682527b4e0bbb1faf7b9c95cfa3a7e07afc61c725e13ce5f5f371b
Tx public key: efe77ff5b927d640ed89b60b8a45310191ef52e1d374103bfad48c7090883349
Timestamp: 1694460277 Timestamp [UCT]: 2023-09-11 19:24:37 Age [y:d:h:m:s]: 01:246:10:48:25
Block: 845999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437270 RingCT/type: yes/0
Extra: 01efe77ff5b927d640ed89b60b8a45310191ef52e1d374103bfad48c709088334902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.965726580000 dcy

stealth address amount amount idx
00: 437353c11c546c3126e6d4c1f7beae66ca2edc93c3811a9bf2e3bc9e8cc12305 0.965726580000 1299433 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 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": 846009, "vin": [ { "gen": { "height": 845999 } } ], "vout": [ { "amount": 965726580, "target": { "key": "437353c11c546c3126e6d4c1f7beae66ca2edc93c3811a9bf2e3bc9e8cc12305" } } ], "extra": [ 1, 239, 231, 127, 245, 185, 39, 214, 64, 237, 137, 182, 11, 138, 69, 49, 1, 145, 239, 82, 225, 211, 116, 16, 59, 250, 212, 140, 112, 144, 136, 51, 73, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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